Whenever I query AvailabilityReplica.Role property it is always Unknown for all the replica servers participating in the AAG except for the one that Im making the call on.
I do not see this problem when I make the call on primary replica server.

Any idea why it behaves like this and how to get the right information? I do not want to make call to each replica server to get the details.

See the output below.

----------------
AAG details:
----------------
AAG name: Lakers_Fluke
AAG Parent: [fluke]
AAG Primary Replica Server Name: LAKERS
AAG State: Existing
AAG Local Replica Role: Secondary
----------------
REPLICA SERVERS FOLLOWS:
----------------

Replica Server 1.

AAG replica name: FLUKE
AAG Parent: [Lakers_Fluke]
AAG State: Existing
AAG replica mode: AsynchronousCommit
AAG SConnection tate: Connected
AAG Operational State: Online
AAG Role: Secondary

Replica Server 2.

AAG replica name: LAKERS
AAG Parent: [Lakers_Fluke]
AAG State: Existing
AAG replica mode: AsynchronousCommit
AAG SConnection tate: Unknown
AAG Operational State: Unknown
AAG Role: Unknown

Replica Server 3.

AAG replica name: WARRIORS
AAG Parent: [Lakers_Fluke]
AAG State: Existing
AAG replica mode: AsynchronousCommit
AAG SConnection tate: Unknown
AAG Operational State: Unknown
AAG Role: Unknown
----------------

What does the SQL Errorlog say? And what are the messages in the AlwaysOn Health XEvent Trace?
Edit: The output of this query would also help:

select

*fromsys.dm_hadr_availability_replica_states

• Edited by PrinceLucifer Tuesday, August 07, 2012 6:19 AM Another idea

Everything looks normal. Here is my observation after connecting to a replica server through SMO and querying for AAG properties...

If the replica server role is not primary, roles of other replica servers in the group are always unknown. If it is primary it gets me the roles of all serves correctly.

Please help me with it.

I still would like to see the output of my query before as well as the SQL Errorlogs from both servers... It might look normal, but maybe there are some details in there that can help us get on the right track

Thanks for trying to get me out of this situation. Please find the logs @ https://docs.google.com/folder/d/0B-vLicWiTuTmTDJrV2ctMUFsUlU/edit

I do not see a replica server role in SQL Server Management Studio as well. Check the screen shot below...

Looking at your logs the DBs look good actually. The AAG2Warriors Group will not show you the information because you are looking at it from the secondary, which does not have the information. If you open it on the primary you will see.

The only thing in the logs that bothers me a little is the errors in Windows Server Failover Cluster that pop up in the SQL Errorlog. But given that your AGs seem all to be up and healthy it's really hard to say what impact this has...

• Proposed as answer by Sakarin Thursday, September 06, 2012 5:33 PM
• Unproposed as answer by Sakarin Thursday, September 06, 2012 5:33 PM

Thanks for looking into this and analyzing the logs.

I'm wondering now, if I'm the only one seeing this issue.

I setup a test environment to repro the issue and I see it the same way you do. Looking through my old mails I can tell you though that this is not by mistake, it is the way it is designed to work... Sorry that I missed that before.

• Marked as answer by amber zhangModerator Monday, August 13, 2012 1:33 AM

Thanks for that. It is sad that MS designed something this way. If you're on a secondary server, there  is no way to find out what his primary server is. He has to logon to all the servers.

• Edited by HemC Monday, August 13, 2012 7:41 PM

Hi Please tell me how to fix this problem thank

You are right i faced with this situation too, but if if you will look at the AON group Dashboard you will be able to see roles of the servers....

Hy

same problem, cluster works perfectly but uknow status is still persistent either after update both sql nodes to the last Cum. updates and S.packs.

May 2015

I found this old article related to SQL sp1, https://support.microsoft.com/en-us/kb/2689367/en-us 

is there a workaround or a clear Microsoft explanation that confirm the "Unknow" GUI visualisation is correct?

Thanks 

I know this is an old necro'd thread but I wanted to add some clarity:

If you're on a secondary server, there is no way to find out what his primary server is. He has to logon to all the servers.

There are actually two easy ways:

1. Connect to the listener if one exists.

2. Use sys.dm_hadr_availability_group_states joined to others if you have multiple AGs

-Sean